chore: set renovate minimumReleaseAge to align with pnpm#10632
Merged
sheremet-va merged 1 commit intoJun 22, 2026
Conversation
pnpm v11 enforces a default minimumReleaseAge of 1440 minutes (1 day) via its lockfile supply-chain verification pass. Renovate had no release-age floor, so it could bump dependencies to versions freshly published within that window, causing the pnpm check to fail in CI. Set Renovate's minimumReleaseAge to 1 day to match. AI-Agent: Opencode
hi-ogawa
changed the title
hi-ogawa
changed the title
sheremet-va
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The last Renovate PR failed due to pnpm minimum release age check #9958. This PR updates renovate config so they don't propose too latest version bump that would be rejected by pnpm.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.